🔧 Changes

Part two of keyword preservation implementation by building off of #738. This PR introduces the ability to recursively traverse an arbitrary JSON structure and look for preservable properties. The recursion here is necessary because the assets tree is an amalgamation of all the different Auth0 resource types which contain their own arbitrary data structures which may differ on a tenant-by-tenant basis.

Notably, this utility of this function is limited because it only produces a list of the field values to preserve which may help us understand what to preserve but it doesn't provide any guidance on where or how to preserve. The concept of "addresses" will be added in a follow-up PR which will improve the usefulness of this function, but wasn't added to keep this PR simple.

📚 References

Related Issues:

#328
#688

🔬 Testing

Added a single unit test that tests a variety of scenarios.

📝 Checklist

• All new/changed/fixed functionality is covered by tests (or N/A)
• I have added documentation for all new/changed functionality (or N/A)